Fix AWS token expiry issue when cached token expires when using AWS Profile for Bedrock (#2469) #2530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix AWS token expiry issue when cached token expires when using AWS Profile for Bedrock (#2469)
Context
When using AWS Bedrock profile setup, the cached token expires which even after refreshing results in having to restart the entire VS Code environment for Roo Code to pull the latest token.
Implementation
The ignoreCache parameter was set to true when creating the clientConfig credentials.
Screenshots
This is the behaviour whilst the session is working and when the token expires.
How to Test
This fix has been used internally with a custom built version of Roo Code for the past month and has been successful with no token expiry issues.
Get in Touch
vagadiya
Important
Fixes AWS token expiry issue by setting
ignoreCache: trueinfromIni()forclientConfig.credentialsinAwsBedrockHandler.ignoreCache: trueinfromIni()forclientConfig.credentialsinAwsBedrockHandler.This description was created by
for 156e5b5. It will automatically update as commits are pushed.